Computing device having programmable state transitions

ABSTRACT

A computing device having programmable state transitions is disclosed. The device includes a real-time clock that generates a signal in response to the real-time clock attaining a programmed time of day. The device additionally includes a processor, coupled to the real-time clock that receives the signal and transitions from a first state to a second state, such as from a hibernate state to a standby state.

BACKGROUND OF THE INVENTION

The invention pertains generally to computing devices and, moreparticularly, to computing devices that transition between operatingstates.

Many computing devices, such as portable laptop computers, handheldcomputers, and processor-based portable messaging devices, include abattery that allows the computing device to be temporarily operated atvirtually any location, without regard to the availability of primarypower from an external source. To extend the length of time that a usercan operate the portable computing device away from the external source,many users carry extra batteries that can be installed when needed tocontinue operating the device.

When portable computing devices are used in office environments, manyusers operate these devices according to predictable schedules. Forexample, a particular computing device user may come to work at acertain time every day, eat lunch at a certain time, and leave at acertain time. During lunch, and after the user leaves the office for theday, the user generally shuts off the computing device so that batterypower can be conserved. This prolongs the life of the battery so thatthe portable computing device is available for use over a period thatmay include several days or longer.

In the event that the user does not remember to shut off the portablecomputing device, the device may remain operational for a lengthy periodof time before being inactivated. Thus, upon returning to the device,the user may find that the computing device's battery has been depleted.This, in turn, requires that the user either replace the battery orreturn to a location where the device can be powered by an externalsource. The need to be constantly attentive to device power consumption,as affected by the operating state of the device, reduces the utility ofthe device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a computing device that programmablytransitions between states in accordance with a preferred embodiment ofthe invention.

FIG. 2 is a graph of computing device power consumption versus time ofday in accordance with a preferred embodiment of the invention.

FIG. 3 is a panel presented to a user in association with a program thatallows the user to input a state transition time schedule into acomputing device in accordance with a preferred embodiment of theinvention.

FIG. 4 is a flowchart for a method used to program a computing device toperform time event driven state transitions in accordance with apreferred embodiment of the invention.

FIG. 5 is a flowchart for a method used by a computing device fortransitioning from a hibernate to a standby state in accordance with apreferred embodiment of the invention.

FIG. 6 is a flowchart for a method of responding to a power managementevent in a computing device having programmable state transitions inaccordance with a preferred embodiment of the invention.

FIG. 7 is a flowchart for a method of responding to a time event used ina computing device having programmable state transitions in accordancewith a preferred embodiment of the invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

A computing device having programmable state transitions allows a userto program the device with times of day at which the device entersparticular operating states. This allows the device's power consumptionto be programmably reduced at certain scheduled times while beingincreased at other times. The program control illustrated by theembodiments herein can allow the battery life of the computing device tobe extended so that the device can be available for use over a longerperiod of time without recharging or replacing an associated battery, orrequiring the user to find an external source with which to power thedevice.

FIG. 1 is a block diagram of a computing device that programmablytransitions between states in accordance with a preferred embodiment ofthe invention. In FIG. 1, processor 100 runs an operating system and mayrun one or more application programs that allow the user of thecomputing device to interact with the computing device to performvarious tasks. These tasks can include, but are not limited to, wordprocessing, electronic mail, spreadsheet calculations, and so forth. Theuser preferably interacts with the computing device of FIG. 1 usinginput device 160, which may include a keyboard, keypad, or other type ofinput device that controls the placement of characters or symbols ondisplay 130. In addition to interacting with input device 160, the usermay also interact with graphical pointing device 170, which may includea mouse, trackpad, trackball, or other device used to position a cursoror other indicator on display 130 of the computing device.

In the embodiment of FIG. 1, switch 180 enables the user to control atleast some of the operating states in which the computing device of FIG.1 is capable of operating. For example, switch 180 may control thetransition from a hibernate state to an active state. In addition toswitch 180, one or both of input device 160 and graphical pointingdevice 170 may also be used to control the operating state of thecomputing device of FIG. 1. Preferably, inputs from switch 180,graphical pointing device 170, and input device 160 are conveyed tokeyboard controller 150. Keyboard controller 150 receives these inputsand requests processor 100 to transition to a particular operatingstate. Keyboard controller 150 also communicates with battery 190 by wayof a logic unit (not shown) that monitors the health and status of thebattery.

Keyboard controller 150 responds to various unscheduled power managementevents that occur within the computing device represented by FIG. 1. Inthe embodiments of the invention described herein, an unscheduled powermanagement event is an event that affects the delivery of operatingpower to the computing device. An example of an unscheduled powermanagement event can be a signal communicated from battery 190indicating that the battery is no longer capable of supplying sufficientcurrent to operate the computing device in its present operating state.Another example of an unscheduled power management event can be the userdepressing switch 180 or interacting with either or both of graphicalpointing device 170 and input device 160 in order to change an operatingstate of the computing device of FIG. 1. These unscheduled powermanagement events are conveyed to processor 100 by way of keyboardcontroller 150.

In a preferred embodiment, a programmed time of day is input by the userof the computing device of FIG. 1. The programmed time of day is storedwithin real-time clock memory 147, which is accessible to real-timeclock 110. When real-time clock 110 attains a time of day that issubstantially equal to the programmed time of day, the real-time clockgenerates a signal that is received by processor 100. In response to thereceived signal, processor 100 reads current time event flag register142 within memory 140. Processor 100 then transitions the computingdevice of FIG. 1 to an operating state requested by the current timeevent flag stored within register 142. Although not shown, real-timeclock 110 preferably makes use of a dedicated battery that providespower to the real-time clock.

In a manner that accords with the input of a single time of day, a userpreferably interacts with the computing device of FIG. 1 to input a setof programmed times of day as well as a time event flag that correspondsto each of the programmed times of day. Each programmed time of day andthe corresponding time event flag are stored as an element of transitionschedule 141 within memory 140. As previously mentioned, in response tothe signal generated by real-time clock 110 attaining a programmed timeof day stored in real-time clock memory 147, processor 100 reads currenttime event flag register 142. After reading current time event flagregister 142 and transitioning the computing device to the appropriateoperating state, processor 100 reads the next element of transitionschedule 141 within memory 140. The next (i.e. upcoming) programmed timeof day is then stored into real-time clock memory 147 and the nextcurrent time event flag is stored in current time event flag register142, thereby preparing the computing device for the next scheduledtransition.

The embodiments of the invention disclosed herein contemplate ahibernate state. In the hibernate state, processor 100 as well as otherfunctional units of FIG. 1, with the exception of real-time clock 110,are not operational. In the hibernate state, the computing device ofFigurel does not consume a substantial amount of power. Prior toentering the hibernate state, processor 100 may perform variousfunctions in which information relative to the user's activities isstored or saved within memory 140, or within other memory mediaaccessible to processor 100 that are not shown in FIG. 1. It iscontemplated that the transition from the hibernate to the active staterequires an amount of time sufficient to be a nuisance or to at least benoticeable to the user.

The embodiments of the invention disclosed herein also contemplate astandby state. In the standby state, processor 100 may retain someoperational capability, but perhaps at a reduced level. Memory 140 mayalso be operational and available to processor 100 in the standby state,while various other devices coupled to processor 100 may not beoperational. These other devices include display 130, input devices, aswell as any hard disks or other memory media that consume power due tothe motion of the media relative to a fixed reading or writingmechanism. In the standby state, real-time clock 110 continues to beoperational. It is contemplated that the transition from the standby tothe active state does not require the length of time needed totransition from the hibernate to the active state.

The embodiments of the invention disclosed herein also contemplate anactive state. In the active state, substantially all of the componentsof FIG. 1 are operational. The active state corresponds to a state inwhich a user may perform various interactions with the computing deviceof FIG. 1. During transitions between states, such as from hibernate tostandby, the computing device represented by FIG. 1 may briefly enterthe active state. This brief entry may be required so that processor 100can perform logic related operations such as reading elements oftransition schedule 141, storing information into memory 140 andreal-time clock memory 147, and so forth.

FIG. 2 is a graph of computing device power consumption versus time ofday in accordance with a preferred embodiment of the invention. In FIG.2, the hibernate, standby, and active states are shown on the verticalaxis as corresponding to various power consumption levels. Thus, when inthe hibernate state, the computing device requires very little power. Inthe standby state, some power is consumed, such as that required tooperate memory 140 of FIG. 1. In the active state, a higher level ofpower is consumed, such as would be required to operate processor 100,display 130, input and pointing devices 160 and 170, memory 140, as wellas any disk drives accessible to processor 100.

The horizontal axis of FIG. 2 shows a time of day. Thus, as each dayprogresses, the computing device of FIG. 1 transitions to certainoperating states according to a programmed schedule that is repeatedeach day. Therefore, in the example of FIG. 2, the computing device isprogrammed to transition from the hibernate state to the standby stateat 6:00 AM. The computing device is maintained in the standby state from6:00 AM until 8:00 AM. At 8:00 AM, the computing device transitions froma standby to an active state. At 12:00 PM, the computing devicetransitions from the active state to hibernate, and transitions back tothe active state at 1:00 PM. From 1:00 PM until 6:00 PM, the computingdevice is maintained in the hibernate state. The device is maintained inthe hibernate state from 6:00 PM until 6:00 AM the following day, whenthe process repeats.

As previously mentioned herein, the times of day at which the variousstate transitions occur are under the control of the user of thecomputing device. Thus, the user may wish to transition from hibernateto standby at an earlier or later time than the 6:00 AM transition timeshown in FIG. 2. Additionally, the user may not wish for the computingdevice to programmably enter the active state at any time of day. Theflexibility to adjust the times of day at which the various statetransitions occur, as well as the states which are transitioned to, arecontemplated as being under the control of the user of the computingdevice. Further, there is no upper limit to the number of transitionsbetween the hibernate, standby, and active states. Thus, the user maychoose numerous transitions between these states throughout the day,week, or other period.

FIG. 3 is a panel presented to the user in association with a programthat allows the user to input a state transition time schedule into acomputing device in accordance with a preferred embodiment of theinvention. FIG. 3 includes fields that allow the user to program thecomputing device with a desired state transition schedule. As shown inthe example of FIG. 3, the computing device has been programmed totransition to the standby state at 6:00 AM, to transition to the activestate at 8:00 AM, to transition into and out of the hibernate state at12:00 PM and 1:00 PM (respectively), and to transition to the hibernatestate at 6:00 PM.

Preferably the “Standby”, “Active”, and “Hibernate” fields of FIG. 3 areselectable. For example, in the event that the user does not wish thecomputing device to programmably enter the hibernate state, the user mayselect “Standby” in lieu of the “Hibernate” selection. In this case, thecomputing device would transition from the standby to the active stateat 8:00 AM and return to the standby state at 6:00 PM.

In an alternate embodiment of the invention, additional columns areadded to the panel of FIG. 3. For example, in the event that the userwishes to transition the computing device to a standby state during adaily meeting time, such as from 9:00 AM until 10:00 AM, for example,additional columns may be added to accommodate these additionaltransitions. Further, additional rows may be added to includetransitions that are desired during weekends and holidays.

FIG. 4 is a flowchart for a method used to program a computing device toperform time event driven state transitions in accordance with apreferred embodiment of the invention. The computing device of FIG. 1,operating in conjunction with an operating system that runs on processor100, is suitable for performing the method. The term “time event” asused herein includes events programmably scheduled by the user. Byperforming the method of FIG. 4, the computing device can be initializedso that time event flags, such as those described in reference to FIG.7, can be responded to.

The method of FIG. 4 begins at block 300 in which a transition schedulepanel, such as that shown in FIG. 3, is presented to a user. The methodcontinues at block 302 in which time event flags, such as the Active,Standby, and Hibernate flags are received. The method continues at block304 in which the computing device receives the times of daycorresponding to the time event flags received in block 302. At block306, each time of day (as programmed by the user) as well as a timeevent flag corresponding to each programmed time of day are stored aselements of a transition schedule within a memory of the computingdevice. Block 306 can also include removing the transition schedulepanel presented to the user in block 300.

The method continues at block 308, in which a determination is made asto whether a time event is currently pending. If a time event iscurrently pending, block 310 is executed in which the time event iscanceled and the method continues at block 312. If a time event is notcurrently pending, the method continues at block 312 without cancelingthe current time event flag.

At block 312, a determination is made as to whether the current time, asreported by a real-time clock for example, corresponds to a currentscheduled active time period. If the current time does correspond to anactive period, block 314 is executed in which the current time eventflag is set to hibernate. This permits the computing device toautomatically transition to hibernate when the next time event occurs,such as would be expected at 6:00 PM in the example of FIG. 2. Themethod then exits at block 316. If the current time does not correspondto a scheduled active time period, the method proceeds directly to theexit block, 316.

FIG. 5 is flowchart for a method used by a computing device fortransitioning between states in accordance with a preferred embodimentof the invention. The computing device of FIG. 1, operating inconjunction with an operating system that runs on processor 100, issuitable for performing the method. The state transitions of FIG. 2 areused for the example of FIG. 5.

The method of FIG. 5 begins at block 320, in which a real-time clockgenerates a signal when the current time of day attains a programmedtime of day. The method continues at block 325, in which a processorreads a current time event flag register in response to receiving thesignal. The method continues at block 330, in which the current timeevent flag is examined to determine if the flag corresponds to atransition to a standby state. If the received time of day event flagdoes correspond to a request to transition to standby, block 340 isexecuted in which the computing device begins the transition to standby.The method continues at block 355 in which the next (or upcoming) timeof day is stored in a memory location accessible to the real-time clock.At block 358, the method continues with storing the current time eventflag that corresponds to time of day stored in block 355. Control thenreturns to block 320, wherein a signal is generated when the currenttime of day attains the programmed time of day stored within the memoryaccessible to the realtime clock. The method of FIG. 5 can then berepeated throughout the day according to a programmed schedule such asthat programmed by way of the transition schedule panel of FIG. 3, forexample.

Retuning now to block 330, if the decision of block 330 indicates thatthe current time event flag is not a transition to a standby state,block 335 is executed in which the current time event flag is evaluatedto determine if the flag is request to transition to an active state. Ifthe decision of block 335 indicates a request to transition to an activestate, block 350 is executed in which the computing device istransitioned to an active state. The method continues at block 355 inwhich in which the next (or upcoming) time of day is stored in a memorylocation accessible to the real-time clock. The method continues atblock 358 with storing the current time event flag that corresponds totime of day stored in block 355. Control then returns to block 320,wherein a signal is generated when the current time of day attains theprogrammed time of day stored within the memory accessible to thereal-time clock.

If the decision of block 335 indicates that the received time of dayevent flag is not a request to transition the computing device to theactive state, block 345 is executed in which the processor transitionsthe computing device to the hibernate state. The method continues atblock 355 in which in which the next time of day is stored in a memorylocation accessible to the real-time clock. The method continues atblock 358 with storing the current time event flag that corresponds totime of day stored in block 355. Control then returns to block 320.

In the embodiment of FIG. 5, various blocks have been included in themethod in order to illustrate details that may be useful in someapplications. However, another method of transitioning between statesmay only require blocks 320, in which a real-time clock generates asignal when the current time of day attains a programmed time of day, aswell as one of blocks 340, and 350 in which a processor transitions froma hibernate to a standby state (block 340) or to an active state (block350) in response to receiving the signal.

FIG. 6 is a flowchart for a method of responding to a power managementevent in a computing device having programmable state transitions inaccordance with a preferred embodiment of the invention. The method ofFIG. 6 handles various programmed power management events, such as thescheduled time events described herein. Additionally, the method of FIG.6 handles unscheduled (or unprogrammed) power management events.

As previously mentioned, an unscheduled power management event is anevent that affects the delivery of operating power to the computingdevice. An example of an unscheduled power management event can be asignal communicated from a battery that indicates the battery is nolonger capable of supplying sufficient current to operate the computingdevice in its present operating state. Another example of an unscheduledpower management event can be the user depressing an “on” switch thatplaces the computing device in the active state, or interacting with aninput device used to initiate a state transition. A further example ofan unscheduled power management event can be a timer-requested statetransition, such as a timeout that automatically transitions thecomputing device after the user has left the device unattended.

The method of FIG. 6 begins at block 500 in which a power managementevent is received. The method continues at block 505 in which adetermination is made as to whether the received power management eventhas been requested by a time event flag. If the received powermanagement event is the result of receiving a time event flag, themethod continues at block 550, in which the computing device waits forthe next power management event flag.

If the received power management event is not the result of receiving atime event flag, meaning that the received power management eventrepresents an unscheduled event, the method continues at block 510 inwhich the current time event flag, such as the flag stored in thecurrent time event register, is canceled. This cancellation prevents thecomputing device from programmably transitioning to an active state whena battery, for example, can no longer provide the required current tooperate the computing device in the active state.

The method continues at block of 520 in which a determination is made asto whether the unscheduled power management event is a request totransition to an active state from a standby or hibernate state. If thedecision of block of 520 indicates that the unscheduled power managementevent is a request to transition to an active state, block 540 isexecuted in which a decision is made as to whether the current time ofday corresponds to a scheduled active period, such as the 1:00 PM to6:00 PM period of FIG. 2. In the event that the current time of daycorresponds to a scheduled active time period, block 560 is executed inwhich the current time event flag is set to either hibernate or standby,depending on the desired programmed state transitions. If the currenttime event flag is programmed to enter the hibernate state, thecomputing device is placed into the hibernate state the next time thereal-time clock attains a programmed time (e.g. 6:00 PM). If the currenttime event flag is programmed to enter the standby state, the computingdevice can be placed into a standby state at the next programmed time.

If the decision of block 540 indicates that the current time of day doesnot correspond to a scheduled active time period (such as from 6:00 PMto 8:00 AM on the following day), the method continues at block 550 inwhich the computing device waits for the next power management eventbefore returning to block 500 and without setting the current time eventflag to hibernate. This can be useful in the event that the user isoperating the computing device in the evening (e.g. after 6:00 PM) anddoes not wish the computing device to transition to hibernate upon thenext programmed time event (e.g. 6:00 AM).

Returning now to block 520, if the decision of block 520 does notindicate that the unscheduled power management event is a request totransition to an active state, block 530 is executed in which adetermination is made as to whether the unscheduled power managementevent is a request to transition to a standby state. If a standby statehas been requested, block 570 is executed in which a decision is made asto whether the current time of day corresponds to a scheduled activetime period (e.g. 8:00 AM to 12:00 PM). If the current time of day doescorrespond to a scheduled active time period, block 590 is executed inwhich the current time event flag is set to hibernate. By setting thecurrent time event flag to hibernate, the computing device is preparedto enter the hibernate state at the next programmed transition time.This can be useful when the user sets the computing device to thestandby state in the afternoon (for example) wherein the next programmedtransition time should place the computing device in hibernate, at 6:00PM. The method then continues at block 550 in which the computing devicewaits for the next power management event.

If the decision of block 570 indicates that the current time of day doesnot correspond to a scheduled active time period, block 600 is executedin which the transition to standby is rejected. Block 610 is thenexecuted in which the current time event flag is set to standby, andblock 620 is executed in which the computing device is requested totransition to hibernate. This can be useful when the user sets thecomputing device to a standby state during a time period thatcorresponds to the computing device's hibernate period (e.g. 6:00 PM to6:00 AM). In this case, setting the current time event flag to standbyand transitioning the device to hibernate allows the device totransition to standby at the next programmed time (such as 6:00 AM).Control then returns to block 550.

Returning to decision block 530, if the decision of block 530 indicatesthat the unscheduled power management event is not a request totransition to a standby state, block 580 is executed in which a decisionis made as to whether the unscheduled power management event is arequest to transition to a hibernate state. If the decision of block 580indicates that the unscheduled power management event is not a requestto transition to a hibernate state, the method returns to block 550 inwhich the device waits for the next power management event. This can beuseful in response to a battery-related event, such as a drop in voltageoutput, in which it may be advantageous for the computing device to waitfor the next power management event, such as the user requesting anactive state after the battery has been charged.

If the decision of block 580 indicates that the unscheduled powermanagement event is a request to transition to a hibernate state, block630 is executed in which the time event flag is set to standby. Controlthen returns to block 550. This can be useful when the user hasrequested the computing device to enter the hibernate state after usingthe device during the scheduled hibernate period (e.g. 6:00 PM to 6:00AM). In this case, the computing device is prepared to enter the standbystate at 6:00 AM.

In FIG. 6, various blocks have been included in the method in order toillustrate details that may be useful in some applications. However,another method of responding to a power management event in a computingdevice having programmable state transitions may only require thecancellation of a current time event flag (block 510), an unscheduledpower management event determination block (such as block 520), acurrent time of day determination block (such as block 540), as well asstoring one of a standby and a hibernate current time event flag inmemory (block 560) if the unscheduled power management event is arequest to transition to an active state and if the current time of daycorresponds to a scheduled active time period.

FIG. 7 is a flowchart for a method of responding to a time event used ina computing device having programmable state transitions in accordancewith a preferred embodiment of the invention. The method of FIG. 7begins at block 700 in which a time event signal is received by aprocessor. The method continues at block 710 in which a current timeevent flag register is read in order to determine the event thatcorresponds to the received time event signal. If the current time eventflag indicates a request to set the computing device to a hibernatestate, block 720 is executed in which the current time event flag is setto standby. By setting the current time event flag to standby, thecomputing device is prepared for the next transition, which, for thestate transitions of FIG. 2, would be the transition to the standbystate (6:00 AM).

The method continues at block 730 in which a decision is made as towhether the computing device is being requested to transition from thestandby state to the hibernate state. If the computer is beingtransitioned from the standby to the hibernate state, block 770 isperformed in which the computing device is transitioned to hibernate.The method continues at block 780 in which the processor waits for thenext time event. If the decision of block 730 indicates that thecomputing device is not being transitioned from standby to hibernate,indicating that the computing device is in an active state, block 760 isexecuted in which a confirmation panel is presented. The confirmationpanel allows a user, who might be interacting with the device, to stopthe programmed transition to the hibernate state. If the user confirmsthe transition, or after a specified time period, the method continuesat block 770 in which the transition to hibernate is requested. Block780 is then executed in which the processor waits for the next timeevent.

Returning now to the decision of block 710, if the current time eventflag read from the current time event flag register does not indicate arequest to set the computing device to hibernate, block 740 is executedin which the time event flag is set to hibernate. The method continuesby executing block 750 in which a transition to hibernate is requested.Block 780 is then executed in which the processor waits for the nexttime event. Control returns to block 700, thus preparing the processorto receive the next time event flag.

In FIG. 7, various blocks have been included in the method in order toillustrate details that may be useful in some applications. However,another method of a responding to a time event used in a computingdevice having programmable state transitions may only requiredetermining if the time event flag is a request to set the computingdevice to a hibernate state (such as in block 710), setting a time eventflag to standby if the time event flag is set to hibernate (such as inblock 720), and requesting the computing device to enter the hibernatestate (such as in block 770).

While the present invention has been particularly shown and describedwith reference to the foregoing preferred and alternative embodiments,those skilled in the art will understand that many variations may bemade therein without departing from the spirit and scope of theinvention as defined in the following claims. This description of theinvention should be understood to include all novel and non-obviouscombinations of elements described herein, and claims may be presentedin this or a later application to any novel and non-obvious combinationof these elements. The foregoing embodiments are illustrative, and nosingle feature or element is essential to all possible combinations thatmay be claimed in this or a later application. Where the claims recite“a” or “a first” element of the equivalent thereof, such claims shouldbe understood to include incorporation of one or more such elements,neither requiring nor excluding two or more such elements.

1. In a computing device having programmable state transitions, a methodfor responding to a power management event, comprising: canceling a timeevent flag stored in a memory location; determining said powermanagement event; storing a second time event flag into said memorylocation, wherein said second time event flag is set to one of a standbyand a hibernate state, said storing occurring if said power managementevent is a request to transition to an active state and if a currenttime of day corresponds to a scheduled active time period; wherein ifsaid power management event is a request to transition to said standbystate and if said current time of day does not correspond to a scheduledactive period, then additionally performing: rejecting said request totransition said computing device to said standby state; setting saidsecond time event flag to standby; and setting said time event flag tohibernate.
 2. The method of claim 1, wherein said second time event flagis a request to transition to said hibernate state.
 3. The method ofclaim 1, wherein said second time event flag is a request to transitionto said standby state.
 4. The method of claim 1, wherein if said powermanagement event is a request to transition to a hibernate state, thenadditionally performing: setting said time event flag to hibernate. 5.In a computing device having programmable state transitions, a methodfor responding to a time event flag, comprising: determining if saidtime event flag is a request to set said computing device to a hibernatestate; setting a second time event flag to standby if said time eventflag is set to hibernate; and requesting said computing device to entersaid hibernate state, wherein if said time event flag is not a requestto set said computing device to a hibernate state, the method furthercomprising: setting said second time event flag to hibernate; andrequesting said computing device to enter a standby state.
 6. The methodof claim 5, additionally comprising prompting a user of said computingdevice to confirm that said computing device should enter said hibernatestate, said prompting being performed prior to said requesting action.7. One or more computer-readable media having computer-readableinstructions thereon, which, when executed by a computer, cause thecomputer to generate a file used to transition from a hibernate to astandby state, the method comprising: canceling a time event flag storedin a memory location; determining said power management event; storing asecond time event flag into said memory location, wherein said secondtime event flag is set to one of a standby and a hibernate state, saidstoring occurring if said power management event is a request totransition to an active state and if a current time of day correspondsto a scheduled active time period, wherein if said power managementevent is a request to transition to said standby state and if a currenttime of day does not correspond to a scheduled active period, thenadditionally performing: rejecting said request to transition saidcomputing device to said standby state; setting said second time eventflag to standby; and setting said time event flag to hibernate.
 8. Oneor more computer-readable media having computer-readable instructionsthereon, which, when executed by a computer, cause the computer togenerate a file used to transition from a hibernate to a standby state,the method comprising: determining if said time event flag is a requestto set said computing device to a hibernate state; setting a second timeevent flag to standby if said time event flag is set to hibernate; andrequesting the computing device to enter the hibernate state, wherein ifsaid time event flag is not a request to set said computing device to ahibernate state, the method further comprising: setting said second timeevent flag to hibernate; and requesting said computing device to enter astandby state.
 9. The computer-readable media of claim 8, wherein themethod further comprises prompting a user of said computing device toconfirm that said computing device should enter said hibernate state,said prompting being performed prior to said requesting action.
 10. Thecomputer-readable media of claim 7, wherein said second time event flagof the method is a request to transition to said hibernate state. 11.The computer-readable media of claim 7, wherein said second time eventflag of the method is a request to transition to said standby state. 12.The computer-readable media of claim 7, wherein if said power managementevent is a request to transition to a hibernate state, then the methodadditionally performing: setting said time event flag to hibernate.